Method and apparatus for distributing content using a mobile device

ABSTRACT

A server receives, from a first mobile device, a request for content identified by a first resource identifier and a set of presence codes. The set of presence codes includes a presence code for the first mobile device and at least one other presence code for one or more mobile devices in proximity to the first mobile device. The server selects a set of allocated resource identifiers associated with one or more presence codes for one or more of the mobile devices in proximity to the first mobile device having the content cached therein. Each allocated resource identifier in the set is different than the first resource identifier. The server then sends to the first mobile device the set of allocated resource identifiers and associated presence codes for use in retrieving the content cached in at least one of the mobile devices in proximity to the first mobile device.

RELATED APPLICATIONS

The present application is related to and claims benefit under 35 U.S.C.§ 119(e) from U.S. Provisional Patent Application Ser. No. 62/199,770,filed Jul. 31, 2015, titled “Methods and Apparatus for DistributingContent using a Mobile Device”, which is commonly owned with thisapplication by Motorola Mobility LLC, the entire contents of which areincorporated herein by reference.

FIELD OF THE DISCLOSURE

The present disclosure relates generally to content distribution withina network and more particularly to methods and apparatus forfacilitating secondary distribution of content from a server using amobile device.

BACKGROUND

5th generation (5G) mobile networks and wireless systems denote the nextmajor phase of mobile telecommunications standards beyond the current 4Gstandards. Expected features of 5G networks include the capability ofsupporting large numbers of wireless devices, including smartphones andmachine-to-machine devices, and pervasive distribution of highdefinition (HD) media, also referred to herein interchangeably ascontent. Such features will inevitably generate a significant amount ofnetwork traffic load, for instance from large numbers of devicesrequesting HD video streaming from media servers. One solution, whichcan lead to increased cost and network complexity, is to provisionnetworks with higher capacity radio and wireline links and highercapacity routing nodes. However, lower cost solutions must also beexplored, particularly solutions that offload at least some of thecontent distribution from the network.

BRIEF DESCRIPTION OF THE FIGURES

The accompanying figures, where like reference numerals refer toidentical or functionally similar elements throughout the separateviews, together with the detailed description below, are incorporated inand form part of the specification, and serve to further illustrateembodiments of concepts that include the claimed embodiments, andexplain various principles and advantages of those embodiments.

FIG. 1 is a schematic diagram illustrating an environment that supportsdistributing content using a mobile device in accordance with someembodiments.

FIG. 2 is a message sequence diagram illustrating collaborativefunctionality and messaging for distributing content using a mobiledevice in accordance with an embodiment.

FIG. 3 is a message sequence diagram illustrating collaborativefunctionality and messaging for distributing content using a mobiledevice in accordance with another embodiment.

FIG. 4 is a message sequence diagram illustrating collaborativefunctionality and messaging for distributing content using a mobiledevice in accordance with another embodiment.

FIG. 5 is a block diagram illustrating internal hardware components of auser device configurable in accordance with some embodiments.

FIG. 6 is a block diagram illustrating internal hardware components of amedia server configurable in accordance with some embodiments.

Skilled artisans will appreciate that elements in the figures areillustrated for simplicity and clarity and have not necessarily beendrawn to scale. For example, the dimensions of some of the elements inthe figures may be exaggerated relative to other elements to help toimprove understanding of embodiments of the present disclosure.

The apparatus and method components have been represented whereappropriate by conventional symbols in the drawings, showing only thosespecific details that are pertinent to understanding the embodiments ofthe present disclosure so as not to obscure the disclosure with detailsthat will be readily apparent to those of ordinary skill in the arthaving the benefit of the description herein.

DETAILED DESCRIPTION

Pursuant to the various embodiments are methods and apparatus forfacilitating secondary distribution of content from a server using amobile device. For example, a first wireless communication device, suchas a mobile device, sends to a server a request for content identifiedby a first resource identifier. The request for content also includes afirst presence code that indicates proximal presence of the firstwireless communication device without identifying a user of the firstwireless communication device. In response thereto, the server sends thecontent to the first wireless communication device for caching and alsosends to the first wireless communication device a second allocatedresource identifier that is different from the first resourceidentifier. The second allocated resource identifier can be used toauthorize other wireless communication devices to retrieve the cachedcontent from the first wireless communication device (also referred toherein as secondary distribution), for instance over a direct wireless,e.g., peer-to-peer or device-to-device, connection.

As indicated, the disclosed embodiments allow offloading of mediadistribution from the media server and also from the network, whereinpeer-to-peer connections are used to retrieve the content from awireless communication device having the content cached therein.Moreover, since the requesting wireless communication device is onlyassociated in the content request with a presence code that has no userspecific information, user equipment (UE) and user identities or othersensitive information need not be disclosed to a third party server toeffectuate the secondary content distribution. It should be noted thatthe acronym “UE” is used in both the singular and the plural, herein,depending on the context.

FIG. 1 illustrates a schematic diagram of an example environment 100within which may be implemented methods and devices for distributingcontent using a mobile device, in accordance with the present teachings.As illustrated, environment 100 includes a public land mobile network(PLMN)-1 112, a PLMN-2 114, the Internet 108, a media server 110 withinthe Internet 108, and three mobile devices or UE, namely a UE-A 102, aUE-B 104, and a UE-C 106.

As described, the devices within the environment 100 operate inaccordance with, consistent with, and are in one or more ways compatiblewith 3^(rd) Generation Partnership Project (3GPP) standards or technicalspecifications (TS). Accordingly, the PLMNs 112 and 114 are 3GPPnetworks containing network elements that are configured to operate andcommunicate within and/or external to the network according to one ormore 3GPP TSs, such as Long-Term Evolution (LTE) networks. Likewise, themobile devices 102, 104, and 106 are also configured to communicate witheach other and/or one or more network elements using 3GPP TSs. However,this communication environment 100 implementation is meant only to serveas an example but in no way limit the disclosed embodiments, which mightalternatively be implemented using other types of network deploymentsand associated communication protocols.

The UE 102, 104, 106 can be representative of a variety of mobiledevices or user equipment, also referred to herein generally as userdevices, including, for example, cellular telephones, personal digitalassistants (PDAs), smart phones, laptop computers, tablets, phablets, orother handheld or portable electronic devices. As shown, the UE are eachconfigured to establish links or connections, for instance wirelesslinks, to one of the networks 112 or 114. For an embodiment, a mobiledevice user is a cellular subscriber of a PLMN that offers proximityservices (ProSe) that enables device discovery and device-to-devicecommunication, e.g. according to 3GPP TS 23.303.

Particularly, proximity services enable a user's mobile device toannounce its presence using a presence code. The presence code enablesanother device to detect proximal presence of the mobile device thatsent the presence code without being made aware of the identity of theuser or the mobile device. For the 3GPP embodiment, the presence code isreferred to herein as a proximity-related services code (or “ProSecode”) and is further referred to in the 3GPP specification as a “ProSeApp Code” because each code can be related with an application such asFacebook, Twitter, etc. As used herein, “proximity,” “close proximity,”and “proximal” denote that two devices are close enough to at leastreceive presence codes that are transmitted, e.g., broadcasted, and candenote physical and/or communicative proximity.

For purposes of the present description, it is assumed that a user ofthe UE-B 104 is a subscriber of the PLMN-2 114, and both the users ofthe UE-A 102 and the UE-C 106 are subscribers of the PLMN-1 112.Accordingly, as shown, the UE-A and UE-C can establish a wireless linkwith a network element in the PLMN-1 112 (in this case a ProSeFunction-1 120) to receive a ProSe code, e.g., a ProSe Code-A and aProSe Code-C, respectively. Likewise, the UE-B can establish a wirelesslink with a network element in the PLMN-2 114 (in this case a ProSeFunction-2 122) to receive a ProSe code, e.g., a ProSe Code-B. For aparticular embodiment, the UE 102, 104, and 106 send, namely broadcast,their ProSe codes over direct wireless links using a wirelesspeer-to-peer (P2P) or device-to-device (D2D) technology such asLTE-Direct (also known as LTE-D2D), Wi-Fi-Direct, Wi-Fi Aware, orBluetooth low energy (BLE).

The following elements are further included within the PLMNs 112 and114, although not shown. More particularly, each PLMN includes an accessnetwork, which can use any type of radio access technology (RAT) for aUE to access and communicate using the PLMN. The access networks can becellular access networks or cellular networks, having at least onecellular tower or base station for facilitating the establishment ofwireless links by user devices to the access networks. For a 3GPPnetwork embodiment, the cellular networks can include Evolved UMTSTerrestrial Radio Access Networks (E-UTRANs) or legacy UTRANs having atleast one eNodeB or NodeB for facilitating wireless links for UE such asthe UE 102, 104, and 106.

Notwithstanding, any other cellular or cellular-based access technologycan be used. Such technologies include, but are not limited to: ananalog access technology such as Advanced Mobile Phone System (AMPS); adigital access technology such as Code Division Multiple Access (CDMA),Time Division Multiple Access (TDMA), Global System for Mobilecommunication (GSM), integrated Digital Enhanced Network (iDEN), GeneralPacket Radio Service (GPRS), Enhanced Data for GSM Evolution (EDGE),etc.; and/or a next generation access technology such as UniversalMobile Telecommunication System (UMTS), Wideband CDMA (WCDMA), etc., orvariants thereof.

The PLMNs 112 and 114 also include a core network. The core networksthat support the E-UTRANs and UTRANs cellular networks are,correspondingly, System Architecture Evolution (SAE) cores, alsoreferred to in the art as Evolved Packet Cores (EPCs). The EPCsubcomponents include a Packet Data Network (PDN) Gateway (PGW), e.g., aPGW-1 116 in PLMN-1 112 and a PGW-2 118 in PLMN-2 114. The PGWs serve asa point of interconnect between the EPC and external Internet Protocol(IP) networks, such as the Internet 108, to route packets between thePDNs. Other EPC subcomponents (not shown) can include, a MobilityManagement Entity (MME), a Serving Gateway (S-GW), a Home SubscriberServer (HSS), etc.

The Internet 108 represents a system of interconnected computer networksthat use the standard Transmission Control Protocol (TCP)/IP suite. Oneexample computer network is a network operated by a media serviceprovider, which includes one or more media servers, e.g., the mediaserver 110. The media server 110 stores and shares media or contentincluding, but not limited to, videos such as YouTube videos or movies,audio such as music, picture files, or other static and/or dynamiccontent, some of which can be HD media. In one example, the media server110 is an origin server, which holds the original content. For anotherexample, the media server 110 is an edge server in a ContentDistribution Network (CDN), which holds a cached copy of the originalcontent. Moreover, for a particular embodiment, the UE and media serveruse Hypertext Transfer Protocol (HTTP) for content identification andtransfer.

Additionally, although not shown, environment 100 can further includeother networks coupled to and supported by the core networks andaccessible to UE 102, 104, and 106. Such networks include, for example:one or more PDNs or one or more Wireless Local Area Networks (WLANs).The WLANs have at least one access point for facilitating wireless linksusing, for instance, Institute of Electrical and Electronics Engineers(IEEE) 802.11 standards, also referred to in the art as Wi-Fitechnology, or using Worldwide Interoperability for Microwave Access(WiMax) technology. A PDN can be, for instance, an enterprise network,an IP Multimedia Subsystem (IMS), etc.

FIG. 2 depicts a message sequence diagram 200 illustrating collaborativefunctionality and messaging for distributing content using a mobiledevice, consistent with the present teachings. Diagram 200 showsfunctionality being performed in at least one device and messages beingexchanged between two or more of the devices of: UE-A 102, UE-B 104,UE-C 106, the media server 110, the ProSe Function-1 120, and the ProSeFunction-2 122. The functionality and message exchanges can be inaccordance with any suitable protocol either standard or proprietaryincluding, but not limited to, OAuth protocol, HTTP, IP, etc. It shouldbe further understood that each “massage exchange” depicted in all themessage sequence diagrams described herein can be performed using one ormore messages sent between the relevant devices. Moreover, informationbeing sent or received with other information, requests, etc. does notlimit the information, requests, etc. to being sent in a single message.

For purposes of implementation scenarios described herein, UE 102, 104,and 106 are all authorized to perform ProSe announcement in specificLTE-D2D radio resources or channels. This authorization can bepre-configured in the UE or provided with OMA-DM or a similar protocol.For example, the 3GPP specifications in TS 24.334 clause 5.1.1 definethat OMA-DM is used for provisioning UE with ProSe authorization data,including the PLMNs in which a UE can perform monitoring and/orannouncing. Moreover, it is assumed that for this embodiment, UE 102,104, and 106 perform the Announce Request procedure as described in TS23.303 and, thereby, each receive a ProSe code from a ProSe function viaa PC3 interface. Namely, UE-A 102 receives ProSe Code-A from ProSeFunction-1 120. UE-B 104 receives ProSe Code-B from ProSe Function-2122, and UE-C 106 receives ProSe Code-C from ProSe Function-1 120. Asmentioned earlier, a ProSe Code does not contain any UE or useridentities and, thus, cannot be used by a receiving device to derivesensitive UE or user information.

UE 102, 104, and 106 can now announce or broadcast their respectiveProSe codes in the appropriate D2D radio channels in order to announcetheir presence to devices in close proximity. For one embodiment, thesecodes are transmitted in the clear. Moreover, each code includes: apseudo-random value called a temporary id in 3GPP specs; a PLMNidentity; and a message integrity code (MIC), as specified in 3GPP TS33.303. The MIC is used to integrity protect and validate the ProSecodes and make sure they are not transmitted by malicious UE. A MICvalue can be, for instance, derived in the UE by hashing the allocatedProSe code and a 128-bit discovery key as specified in 3GPP TS 33.303.The discovery key is sent to UE during the Announce Request procedure.

At a point in time, UE-A 102 announces 202 ProSe Code A. However, it isassumed that during this time, neither UE-B 104 nor UE-C 106 is inproximity to UE-A 102. Also during this time, UE-A 102 sends a contentrequest message 204 to the media server 110 for content identified by aresource identifier. For example, the content request message 204 is anHTTP GET message used to request a HD video file identified by a UniformResource Identifier (URI), e.g., URI1. Additionally, the content requestmessage 204 contains ProSe Code-A for UE-A 102. For an embodiment, whenthe media server 110 receives the content request message 204 with theURI1 and ProSe Code-A, the media server 110 detects the PLMN identity asPLMN-1 112 from the ProSe Code-A and contacts 206 the ProSe Function-1120 to validate the ProSe Code-A. In this illustrative scenario, a mediaservice operator has a business agreement with a PLMN-1 operator thatauthorizes the media server 110 to communicate with ProSe Function-1 120over an interface 126. For one example, the interface 126 is similar toa PC2 interface specified in 3GPP TS 23.303 but includes enhancedfunctionality not currently supported in the 3GPP TSs, which allows theexchange of messaging 206 for the ProSe Function-1 120 to validate aProSe code for the media server 110. For a particular embodiment, onceProSe Code-A has been validated, messaging 206 is not repeated if UE-A102 subsequently requests different content from the media server 110.

The ProSe Function-1 120 validates ProSe Code-A by using its MIC valueand an associated Discovery Key. The Discovery Key is available at ProSeFunction-1 120, which previously assigned the ProSe code to UE-A.Validating the ProSe Code-A is useful in that it helps prevent maliciousUE from providing arbitrary ProSe codes to the media server 110. If thevalidation fails, the media server 110 simply provides to UE-A 102 acontent response that includes the requested content, or the mediaserver 110 may ignore the content request 204. However, uponsuccessfully validating the ProSe Code-A (e.g., receiving an indicationfrom the ProSe Function-1 120 that the ProSe Code-A is valid) the mediaserver 110 sends a content response message 208 that includes therequested content as well as an allocated resource identifier, e.g.,URI-A, which is different from the URI1 that UE-A 102 included in thecontent request message 204. UE-A 102 can then cache or store 210 thecontent and associate the cached content with the URI-A resourceidentifier and may also present the content on a display for viewing bya user of UE-A 102.

For example, the content response message 208 is an HTTP 200 OK message.For a particular embodiment, the content response message 208 alsoindicates to UE-A 102, for instance using a cache-control header, thatthe requested content is cacheable, meaning that UE-A 102 can cache itfor some duration or lifetime. The URI-A included in the contentresponse message 208 essentially authorizes receipt, by another device,of the cached content associated with this allocated URI. Accordingly,if another device were to request the content cached at 210 usinganother URI (including the URI1 that the UE-A 102 provided to the mediaserver 110), the UE-A 102 would not provide the cached content. Devicescan only retrieve the content cached at 210 using the allocated URI-A,thereby providing a controlled mechanism for offloading mediadistribution from the media server 110 and from the PLMNs.

Assume now that UE-B 104 and UE-C 106 are in close proximity with UE-A102 as shown in FIG. 1 and, along with UE-A 102, are also announcingtheir respective ProSe codes. As such, at 212: UE-A 102 receives ProSeCode-B from UE-B 104 and ProSe Code-C from UE-C 106; UE-B 104 receivesProSe Code-A from UE-A 102 and ProSe Code-C from UE-C 106; and UE-C 106receives ProSe Code-B from UE-B 104 and ProSe Code-A from UE-A 102.

Additionally, for this embodiment, at 212, the UE determine or derive aquality indicator (QI) associated with each device from which itreceived a ProSe code. The QI indicates an expected quality ofcommunication between the device receiving a ProSe code and the devicesending the ProSe code. For one example, the QI corresponds to, isderived from, is a function of, etc., the received signal strength ofthe received ProSe announcement such that QI values indicating a higherquality of communications are derived for announcing UE that are closerto the receiving UE. Accordingly, at 212: UE-A 102 determines QIs forUE-B 104 and UE-C 106; UE-B 104 determines QIs for UE-A 102 (e.g., QI-A)and UE-C 106 (e.g., QI-C); and UE-C 106 determines QIs for UE-B 104 andUE-A 102.

Subsequently, UE-B 104 sends a content request message 214, e.g., anHTTP GET message, to the media server 110 to request the contentidentified using URI1. For this embodiment, besides the URI1, thecontent request message 214 also contains a set of one or more ProSecodes, which includes ProSe Code-B and the ProSe codes of any proximalUE along with the QIs determined for the proximal UE. Accordingly, thecontent request message 214, along with ProSe Code-B for the UE-B 104,also contains the ProSe Code-A with the associated QI-A and the ProSeCode-C with the associated QI-C.

Upon receiving the content request message 214, and if it has notalready done so, the media server 110 validates ProSe Code-B todetermine whether to respond with the content or redirect the UE-B 104to receive the content directly from another mobile device. In thiscase, let's assume that the media server operator does not have abusiness agreement with the operator of PLMN-2 114. Thus, the mediaserver 110 does not have an interface to the ProSe Function-2 122.Accordingly, when the media server 110 detects the PLMN identity for theProSe Code-B as PLMN-2 114, the media server 110 contacts 216 the ProSeFunction-1 120 to validate the ProSe Code-B. ProSe Function-1 120 thencontacts 218 ProSe Function-2 122 over an interface 124 to validate theProSe Code-B, which ProSe Function-2 122 can do using the MIC value. Forone example, the interface 124 is similar to a PC6 interface specifiedin 3GPP TS 23.303 but includes enhanced functionality not currentlysupported in the 3GPP TSs, which allows the exchange of messaging 218for the ProSe Function-2 122 to validate a ProSe code for the ProSeFunction-1 120.

If validation fails, the media server 110 simply sends UE-B 104 therequested content for caching, or the media server 110 may ignore thecontent request 214. However, upon successful validation of ProSeCode-B, the media server 110 can proceed to offload, to a non-networkdevice, distribution of the requested content associated with the URI1.In this case, the media server 110 selects 220 UE-A 102, which wasallocated URI-A, for distributing the requested content to UE-B 104.More particularly, the media server 110 determines which of the UEhaving ProSe codes included in the content request message 214 has afresh, i.e., the lifetime hasn't expired, cached copy of the requestedcontent. The media server 110 can do this by determining whether any ofthese UE has been allocated a resource identifier, other than URI1,associated with the requested content.

For one implementation scenario, the media server 110 determines thatonly the UE having ProSe Code-A has a fresh cached copy of the requestedcontent. For another implementation scenario, the media server 110determines that both the UE having ProSe Code-A and the UE having ProSeCode-C have a fresh cached copy of the requested content. In the lattercase, the media server 110 can select the “best” UE between these two UEfor redirecting the content request based on the QIs provided with theirProSe codes. For example, the media server 110 determines that the UEassociated with ProSe Code-A 102 would be the best UE for redirectingthe content request since QI-A indicates that the expected quality ofcommunications with the associated UE would be better than the expectedquality of communications with the UE associated with the QI-C.

For a further embodiment, not all UE that are allocated valid ProSecodes are authorized to perform ProSe D2D communications, for instancebased on their subscriptions. Namely, ProSe D2D communication may beallowed with some UE but not with others. Accordingly, the media server110 determines if UE-A 102 and UE-B 104 are authorized for ProSecommunications. For an embodiment, this determination can be skipped ifthe media server 110 has already determined such authorization andstored the results. Again, since the media server 110 is only authorizedto communicate with the ProSe Function-1 120, this determinationinvolves messaging 222 between the media server 110 and the ProSeFunction-1 120 over the interface 126 as well as messaging 224 betweenthe ProSe Function-1 120 and the ProSe Function-2 122 over the interface124. For example, the ProSe Function-1 120 has access to subscriptionand other sensitive information for a user of UE-A 102, which wasallocated ProSe Code-A, to determine whether UE-A 102 is authorized forProSe D2D communications. Likewise, the ProSe Function-2 122 has accessto subscription and other sensitive information for a user of UE-B 104,which was allocated ProSe Code-B, to determine whether UE-B 104 isauthorized for ProSe D2D communications.

For one embodiment, where either UE-A 102 or UE-B 104 is unauthorizedfor ProSe communication, the media server 110 simply sends the requestedcontent to UE-B 104. If both UE-A 102 and UE-B 104 are authorized forProSe communication, the media server 110 sends a redirect responsemessage 226 to the UE-B 104 to redirect the UE-B 104 to instead retrievethe requested content, using the URI-A, from the UE associated with theProSe Code-A. Accordingly, the redirect response message 226 includesthe URI-A and associated ProSe Code A. The URI-A is used to preventmalicious UE from retrieving content from nearby caches (UE) when theyare not authorized by the network to perform ProSe communication.Indeed, UE-B 104 can request and received the cached content from UE-A102 only if UE-B 104 knows the URI-A, which is the allocated URI thatcorresponds to the content cached at 210. For a particular embodiment,the redirect response message 226 is a Temporary Redirect messagesupported by HTTP version 1.1.

For this illustrated embodiment, the redirect response message 226 alsoincludes a URI-B allocated to UE-B 104 to authorize other devices toretrieve from UE-B 104 the cached content associated with URI1. TheURI-B is necessarily different from URI1 but can be the same ordifferent from URI-A allocated to UE-A 102 or a URI-C allocated to UE-C106, depending on the allocation mechanism used by the media server 110.

Upon receiving the redirect response message 226 with the URI-A, theUE-B 104 establishes 228 D2D ProSe communication with the UE thatannounced ProSe Code-A, in this case UE-A 102. Any suitable methods canbe used to establish 228 the ProSe communication including, but notlimited to, LTE Direct, Wi-Fi Direct, Wi-Fi Aware, Bluetooth, etc.,whereby in one example, the UE-B uses the ProSe Code-A to establish theD2D ProSe communication with the UE-A. Using the D2D link, the UE-B 104sends a content request message 230, e.g., a HTTP GET message, directlyto UE-A 102, which contains the URI-A. Since the UE-A 102 has associatedthe URI-A with the content cached at 210, the UE-A 102 sends a contentresponse message 232, e.g., a HTTP 200 OK message, which directlyprovides this content to UE-B 104. UE-B 104 then caches 234 the contentand associates the content with URI-B allocated by and received from themedia server 110.

FIG. 3 depicts a message sequence diagram 300 illustrating collaborativefunctionality and messaging for distributing content using a mobiledevice, consistent with the present teachings. Diagram 300 showsfunctionality being performed in at least one device and messages beingexchanged between two or more of the devices of: UE-A 102, UE-B 104,UE-C 106, the media server 110, the ProSe Function-1 120, and the ProSeFunction-2 122. The functionality and message exchanges can be inaccordance with any suitable protocol either standard or proprietaryincluding, but not limited to, OAuth protocol, HTTP, IP, etc.

For a particular implementation scenario, devices 102, 104, 106, 110,and 120 collaboratively perform functionality and messaging 202, 204,206, 208, 210, and 212 as described above. Accordingly, the media server110 has allocated URI-A to UE-A 102 as described above, and the UE 102,104, and 106 have announced and received one another's ProSe codes, withthe exception that at 212 the UE need not determine the QIs associatedwith each UE from which it received a ProSe code.

Accordingly, in this embodiment, when the UE-B 104 sends to the mediaserver 110 a content request message 302 requesting content identifiedby the URI1, the message 302 contains the set of ProSe codes (e.g., theProSe Code-A, ProSe Code-B, and ProSe Code-C) without the QI. As before,the media server 110 can validate the ProSe Code-B using the messaging216 and 218. Once the ProSe Code-B is successfully validated orverified, the media server 110 determines 304 which of the neighbors(i.e., devices for which UE-B 104 provided the ProSe codes) have beenallocated a special URI for the requested content, which in this examplescenario is the UE associated with ProSe Code-A and the UE associatedwith ProSe Code-C. For an embodiment, using messaging 310 and 224 themedia server 110 determines which of UE-A, UE-B, and UE-C are authorizedto perform ProSe communication. Similar to with ProSe Code-A and ProSeCode-B, the media server 110 can also validate the ProSe Code-C, forinstance using messaging 310, if such validation has not alreadyoccurred. It is assumed that all three UE are authorized for ProSecommunication such that UE-B can retrieve the content either from UE-Aor from UE-C. Alternatively, if the media server determines that UE-A,for instance, is not authorized for direct communication, the mediaserver 110 will request UE-B to retrieve the content from UE-C.

The media server 110 sends a redirect response message 306 to the UE-B104 that includes the URI-A and associated ProSe Code-A (for UE-A 102),the URI-C and associated ProSe Code-C (for UE-C 106), and the URI-B. At308, the UE-B 104 determines the QIs for communications with the UEannouncing ProSe Code-A and ProSe Code-C and selects a UE for retrievingthe requested content based on the QI. In this case, the UE-B 104selects the UE announcing ProSe Code-A (e.g., UE-A) for retrieving therequested content. UE-B 104 establishes 228 D2D ProSe communicationswith the UE that announced ProSe Code-A, in this case UE-A 102. Usingthe D2D link, the UE-B 104 sends the content request message 230directly to UE-A 102, which contains the URI-A. Since the UE-A 102 hasassociated the URI-A with the content cached at 210, the UE-A 102 sendsa content response message 232 that directly provides this content toUE-B 104. UE-B 104 then caches 234 the content and associates thecontent with URI-B allocated by and received from the media server 110.

FIG. 4 depicts a message sequence diagram 400 illustrating collaborativefunctionality and messaging for distributing content using a mobiledevice, consistent with the present teachings. Diagram 400 showsfunctionality being performed in at least one device and messages beingexchanged between two or more of the devices of: UE-A 102, UE-B 104,UE-C 106, the media server 110, the ProSe Function-1 120, and the ProSeFunction-2 122. The functionality and message exchanges can be inaccordance with any suitable protocol either standard or proprietaryincluding, but not limited to, OAuth protocol, HTTP, IP, etc.

For a particular implementation scenario, devices 102, 104, 106, 110,and 120 collaboratively perform functionality and messaging 202, 204,206, 208, 210, and 212 as described above. Accordingly, the media server110 has allocated URI-A to UE-A 102 as described above, and the UE 102,104, and 106 have announced and received one another's ProSe codes aswell as determined the QIs associated with each UE from which itreceived a ProSe code. Moreover, the content that UE-A 102 requested,received, cached, and associated with the URI-A is an object, e.g.,Object 1. An object, as used herein, refers to any content such as videocontent, audio content, etc.

UE-B 104 sends a content request message 402 to the media server 110 torequest content identified using URI2, which is content that refers tothe content identified by the URI1. For this embodiment, the URI2identifies a web page that contains links to or has embedded thereinObjects 1 to 5, for instance with each object being identified by adifferent URI. Besides the URI2, the content request message 402contains a set of one or more ProSe codes, which includes ProSe Code-Band the ProSe codes of any proximal UE along with the QIs determined forthe proximal UE. Accordingly, the content request message 402 along withProSe Code-B for the UE-B 104 also contains the ProSe Code-A with theassociated QI-A and the ProSe Code-C with the associated QI-C. Asbefore, the media server 110 can validate the ProSe Code-B using themessaging 216 and 218.

Once the ProSe Code-B is validated or verified, the media server 110determines 404 which of the neighbors (i.e., devices for which UE-B 104provided the ProSe codes) have been allocated a special URI for any ofthe Objects 1 to 5 and of those neighbors, which is the best neighborfor offloading content distribution based on the QIs provided. Thedetermining 404 could be very useful where UE-B 104 is in proximity tomany other devices at varying levels of quality of communication, manyof which have already cached objects that the UE-B 104 has requested.For this simplified scenario, the media server 110 selects the UEassociated with ProSe Code-A for distributing the Object 1 and the UEassociated with ProSe Code-C for distributing the Object 2. For anembodiment, using messaging 310 and 224 the media server 110 determineswhich of UE-A, UE-B, and UE-C are authorized to perform ProSecommunication. Similar to with ProSe Code-A and ProSe Code-B, the mediaserver 110 can also validate the ProSe Code-C, for instance usingmessaging 310, if such validation has not already occurred. It isassumed that all three UE are authorized for ProSe communication suchthat UE-B can retrieve the Object 1 from UE-A and Object 2 from UE-C.Alternatively, if the media server 110 determines that UE-A, forinstance, is not authorized for direct communication, the media server110 will request UE-B to retrieve only Object 2 from UE-C.

The media server 110 sends a content response message 408 to the UE-B104 having the URI-B and the web page content that includes, as a linkfor Object 1, the URI-A associated with ProSe Code-A (for UE-A 102) and,as a link for Object 2, the URI-C associated with ProSe Code-C (for UE-C106). To retrieve the content of Object 1 and Object 2, after receivingthe response message 408, the UE-B requests this content from UE-A 102and UE-C 106 by using URI-A and URI-C, respectively. The contentresponse message 408 also includes the links for Objects 3-5, which arealso embedded content to the page request in content request 402.However, since Objects 3-5 are not cached in a UE in close proximity toUE-B 104, the links for these objects point to content that cannot beretrieved from UE-A or UE-C, but instead points to content in the mediaserver 110 or to any other content provider or non-mobile device entityon the Internet 108. In other words, the distribution of Objects 3-5 isnot offloaded to another device.

Accordingly, UE-B 104 establishes 228 D2D ProSe communication with theUE that announced ProSe Code-A, in this case UE-A 102, and establishes410 D2D ProSe communication with the UE that announced ProSe Code-C, inthis case UE-C 106. Using the D2D link, the UE-B 104 sends the contentrequest message 230 directly to UE-A 102, which contains the URI-A, andreceives the Object 1 in the content response message 232. Similarly,using the D2D link, the UE-B 104 sends a content request message 412directly to UE-C 106, which contains the URI-C, and receives the Object2 in a content response message 414. UE-B 104 then caches 416 thecontent (e.g. the web page) received in response 408 and associates thiscontent with URI-B allocated by and received from the media server 110.

FIG. 5 shows a block diagram illustrating example internal hardwarecomponents of a user device 500, for example UE 102, 104, and 106 asillustrated in FIG. 1, which can be configured to facilitateimplementation of embodiments according to the present teachings.“Adapted,” “operative,” “capable” or “configured,” as used herein, meansthat the indicated device or components are implemented using one ormore hardware elements, which may or may not be programmed with softwareand/or firmware as the means for the indicated components to implementtheir desired functionality.

As shown in FIG. 5, the internal hardware elements or components of thedevice 500 include at least one of each of a processor 502, an inputcomponent 504, a communication interface 506, a memory component 508, anoutput component 510, and optionally a set of sensors 512, for instancewhere device 500 is a portable device. As further illustrated, theinternal components of the device 500 are operatively coupled to oneanother, and in communication with one another, by way of one or moreinternal communication links 514, for instance an internal bus.

A limited number of device components 502, 504, 506, 508, 510, 512, and514 are shown for ease of illustration, but other embodiments mayinclude a lesser or greater number of such components in the device 500.Moreover, other well-known elements needed for a commercial embodimentof the device 500 may be omitted from FIG. 5 for brevity. Additionally,the user device 500 is configurable through one or more of its devicecomponents 502, 504, 506, 508, 510, 512, and 514 to operate, forinstance, as a UE in accordance with the embodiments described above byreference to the message sequence diagrams 200, 300, and 400 illustratedin FIGS. 2, 3, and 4.

We now turn to a brief description of the components within theschematic diagram 500. The communication interface 506 allows forcommunication between the user device 500 and other electronic devices,such as a ProSe server, a media server, or another user device. For oneembodiment, the communication interface 506 includes one or morewireless transceivers such as a cellular transceiver, a WLANtransceiver, and a Global Positioning System (GPS) transceiver. Moreparticularly, the cellular transceiver is configured to implement anysuitable cellular or cellular-based technology to conduct cellularcommunications of data over a cellular network. The WLAN transceiver canbe a Wi-Fi transceiver configured to conduct Wi-Fi communications over aWi-Fi network, in accordance with the IEEE 802.11 (a, b, g, n, or ac)standard. The communication interface 506 can also include one or morewireless transceivers configured to implement P2P communications usingtechnology such as LTE Direct, Wi-Fi Direct, Wi-Fi Aware, BLE, etc.Where, for instance, the device 500 is a fixed device, the communicationinterface 506 can include a wired communication interface used tocommunicate through a cable modem or a digital subscriber line (DSL).

The processor 502 includes arithmetic logic and registers necessary toperform the digital processing required by the device 500 to, forexample, facilitate secondary distribution of media from a server in amanner consistent with the embodiments described herein. For oneembodiment, the processor 502 represents a primary microprocessor orcentral processing unit (CPU) of the device 500 such as an applicationprocessor of a smartphone. In another embodiment, the processor 502represents a baseband processor or other ancillary or standaloneprocessor to the CPU that is used by one or more wireless transceivers.Depending, at least in part, on the particular function being performedand a given device 500 design, various functionality or protocols may beexecuted by the processor 502 in hardware or as software or firmwarecode.

For one example, the processor 502 implements a protocol stack orprotocol suite having multiple “layers” that each have, include,contain, or implement one or more protocols, procedures, and/oralgorithms that enable various functionality of the device 500. One suchlayer is an application layer that contains or implements variousapplications installed on the device 500 including, but not limited to,an Internet Protocol multimedia subsystem (IMS)-based application thatsupports voice or video over IP, an application that communicates with aProSe server, etc.

For an embodiment, the input component 504 includes: one or more visualinput components such as a camera lens and photosensor; one or moreacoustic receiver or audio input components such as one or moretransducers (e.g., microphones); and one or more mechanical inputcomponents such as a touchscreen display, a flip sensor, a keyboard, akeypad selection button, and/or a switch. Moreover, the output component510 can include: one or more visual output components such as a liquidcrystal display and/or a light emitting diode indicator; one or moreaudio output components such as a speaker, an alarm, and/or a buzzer;and one or more mechanical output components such as a vibratingmechanism. The sensors 512 can be arranged within a sensor hub to manageone or more functions of the sensors. Example sensors 512 include, butare not limited to, proximity sensors (e.g., a light detecting sensor,an ultrasound transceiver, or an infrared transceiver), touch sensors,altitude sensors, an accelerometer, a tilt sensor, and a gyroscope, toname a few.

The memory component 508 represents one or more memory elements of anyof a variety of forms, for example read-only memory, random accessmemory, static random access memory, dynamic random access memory, etc.In an embodiment, the processor 502 uses the memory component 508 tostore and retrieve data. In some embodiments, the memory component 508is integrated with the processor 502 into a single component such as onan integrated circuit. However, such a single component still usuallyhas distinct portions/sections that perform the different processing andmemory functions. The data that is stored by the memory component 508includes, but need not be limited to, operating systems, programs (e.g.,applications, protocols, and other code), and informational data.

For an embodiment, the user device (referred to as a first mobiledevice, e.g., UE-B) performs a method for enabling secondarydistribution of content received from a server. The method includessending, to a first server (e.g., 110), a first request (e.g., 214) forcontent identified by a first resource identifier (e.g., URI1) andsending, with the first request for content, a set of presence codesthat each indicate proximity of a mobile device without identifying auser of the mobile device. The set of presence codes includes a firstpresence code (e.g., ProSe Code-B) for the first mobile device and atleast a second presence code (e.g., ProSe Code-A and ProSe Code C) for asecond mobile device (e.g., UE-A). The method further includes receiving(e.g., 226), from the first server, at least a second allocated resourceidentifier (e.g., URI-A) and the associated second presence code (e.g.,ProSe Code A), wherein the second allocated resource identifier isdifferent from the first resource identifier. Receiving the secondallocated resource identifier and the associated second presence coderedirects receipt of the first content from the server to the secondmobile device. For example, sending each presence code includes sendinga proximity-related services code allocated by a proximity servicesfunction (e.g., 120, 122) of a 3^(rd) Generation Partnership Projectnetwork (e.g., PLMN-1, PLMN-2) subscribed to by at least one of themobile devices to which the proximity-related services code wasallocated or a user of the mobile device.

For a further embodiment, the method performed by the first mobiledevice includes receiving, from the server, a third allocated resourceindicator (e.g., URI-B), which authorizes receipt of the first contentwhen cached in the first mobile device. When the first mobile devicereceives, from a third mobile device, a second request for the firstcontent, it sends the first content to the third mobile device when thefirst content is identified in the second request by the third allocatedresource identifier (e.g., URI-B) associated with the first presencecode (ProSe Code-B) for the first mobile device. Otherwise, the firstmobile device withholds sending the first content to the third mobiledevice when the first content is identified in the second request by thefirst resource identifier (e.g., URI1).

For the embodiment where the set of presence codes includes one or moreadditional presence codes for one or more additional mobile devices, themethod further includes sending, with the first request (214) for thefirst content, a set of quality indicators (e.g., QI-A, QI-C) indicatingquality of communication between the first mobile device and the secondmobile device and indicating quality of communication between the firstmobile device and each of the one or more additional mobile devices.Alternatively, the first mobile device determines (at 308) set ofquality indicators indicating quality of communication between the firstmobile device and the second mobile device and indicating quality ofcommunication between the first mobile device and each of the one ormore additional mobile devices. The first mobile device receives (at306) a plurality of allocated resource identifiers and associatedpresence codes, which includes the second allocated resource identifier.Each received allocated resource indicator authorizes receipt of thefirst content from a different one of the mobile devices having apresence code in the set of presence codes. The first mobile device thenselects (at 308) based on the set of quality indicators, one of thereceived allocated resource identifiers and associated presence codes(e.g., URI-A/ProSe Code-A) for use in requesting (230) the first contentfrom the mobile device to which the selected resource identifier wasallocated.

FIG. 6 shows a block diagram illustrating example internal hardwarecomponents of a server 600, for example media server 110 as illustratedin FIG. 1. As shown in FIG. 6, the internal hardware elements orcomponents of the media server 600 include at least one of each of aprocessor 602, a communication interface 604, and a memory component606. As further illustrated, the internal components of the media server600 are operatively coupled to one another, and in communication withone another, by way of one or more internal communication links 608, forinstance an internal bus. A limited number of device components 602,604, 606, and 608 are shown for ease of illustration, but otherembodiments may include a lesser or greater number of such components inthe media server 600. Moreover, other well-known elements needed for acommercial embodiment of the media server 600 may be omitted from FIG. 6for brevity.

In general, at a hardware level, the device components 602, 604, 606,and 608 function as described for the analogous device components 502,506, 508, and 514, respectively, shown in FIG. 5. However, one or moreof the device components 602, 604, 606, or 608 may have some additionalfeatures. The communication interface 604, for example, might supportmore simultaneous connections than the communication interface 506, andthe processor 602 might be configured for a greater computational loadas compared to the processor 502. Nonetheless, the media server 600 isconfigurable through one or more of its device components 602, 604, 606,and 608 to operate, for instance, as a media server in accordance withthe embodiments described above by reference to the message sequencediagrams 200, 300, and 400 illustrated in FIGS. 2, 3, and 4.

For a particular embodiment, the server 600 is configured, e.g., by theoperative coupling and collective configuration of its processor 602 andcommunication interface 604, to distribute content using a mobiledevice. Namely, the server 600 receives, from a first mobile device(e.g., UE-A), a first request (e.g., 204) for first content identifiedby a first resource identifier (e.g., URI1) and receives, with the firstrequest for the first content, a first presence code (e.g., ProSeCode-A) that indicates proximity of the first mobile device withoutidentifying a user of the first mobile device. The server 600 sends(e.g., at 208) the first content to the first mobile device. The server600 also sends with the first content a second allocated resourceidentifier (e.g., URI-A) that is different than the first resourceidentifier (URI1). The second allocated resource identifier (URI-A) isassociated with the first presence code (ProSe Code-A) for the firstmobile device and enables receiving the first content cached in thefirst mobile device.

For another embodiment, the server 600 performs a method that includesreceiving, from a different mobile device (e.g. UE-B or a requestingmobile device), a request (e.g., 214, 302, or 402) for the first contentidentified by the first resource identifier (URI1). The server 600receives with the request for the first content, a set of presence codesthat each indicate proximity of a mobile device without identifying auser of the mobile device. The set of presence codes includes a presencecode (e.g., ProSe Code-B) for the requesting mobile device (UE-B) and atleast one other presence code for one or more mobile devices inproximity to the requesting mobile device. The server 600 selects (e.g.,220, 304, or 404) a set of allocated resource identifiers associatedwith one or more presence codes, in the set of presence codes, for oneor more of the mobile devices in proximity to the requesting mobiledevice having the first content cached therein. Each allocated resourceidentifier in the set is different than the first resource identifier(URI1). The server 600 sends (e.g., at 214, 306, or 408), to therequesting mobile device, the set of allocated resource identifiers andassociated presence codes for use in retrieving the first content cachedin at least one of the mobile devices in proximity to the requestingmobile device.

For a further embodiment, the method performed by the server 600includes successfully validating (e.g., 216, 218) the presence code(ProSe Code-B), and the set of allocated resource identifiers andassociated presence codes is sent to the requesting mobile device inresponse to successfully validating the presence code. For example,successfully validating the presence code includes exchanging messaging(216) between the server and a first proximity services function (e.g.,ProSe Function-1) within a first 3^(rd) Generation Partnership Projectnetwork (e.g., PLMN-1) with which the server is authorized tocommunicate. Moreover, successfully validating the presence code canfurther include a message exchange (218) between the first proximityservices function and a second proximity services function (e.g., ProSeFunction-2) within a second 3^(rd) Generation Partnership Projectnetwork (e.g., PLMN-2) subscribed to by at least one of the requestingmobile device or a user of the requesting mobile device. Furthermore,selecting the set of allocated resource identifiers can further include(e.g., at 310 and/or 224) one or both of: validating the one or morepresence codes for the one or more mobile devices in proximity to therequesting mobile device having the first content cached therein; orverifying that the one or more mobile devices in proximity to therequesting mobile device having the first content cached therein areauthorized for proximity communications.

For an embodiment, e.g., by reference to FIG. 2, the set of allocatedresource identifiers and associated presence codes contains only asingle allocated resource identifier and associated presence code (e.g.,URI-A/ProSe Code-A). For this embodiment, the method further includesreceiving, with the request for the first content, a plurality ofquality indicators. Each QI indicates quality of communication betweenthe requesting mobile device and a different one of the mobile devicesin proximity to the requesting mobile device, which has a presence codein the set of presence codes. The single allocated resource identifierand associated presence code is selected (220), based on the pluralityof quality indicators, from multiple allocated resource identifiers andassociated presence codes for multiple mobile devices in proximity tothe requesting mobile device having the first content cached therein.For another embodiment, e.g., by reference to FIG. 3, the set ofallocated resource identifiers and associated presence codes includesmultiple allocated resource identifiers and associated presence codes.This enables the requesting mobile device to select (308) a single oneof the multiple allocated resource identifiers and associated presencecodes for use in retrieving (230, 232) the first content cached in oneof the mobile devices in proximity to the requesting mobile device.

For yet another embodiment, e.g., by reference to FIG. 4, the firstcontent is a first object (e.g., Object 1) referred to in the request(402). In one example, the request (402) is for a web page referring tothe first content as the first object. The request (402) can alsoinclude other objects (e.g., objects 2-5). In this case, the set ofallocated resource identifiers can include at least second and thirdallocated resource identifiers and associated second and third presencecodes (e.g., URI-A/ProSe Code-A and URI-C/ProSe Code-C), of the set ofpresence codes, for use in retrieving the first and second objects(e.g., Objects 1 and 2) from two different mobile devices in proximityto the requesting mobile device.

For a particular implementation, sending the set of allocated resourceidentifiers includes sending a content response (408) to the requestingmobile device that includes, as a first link to the first object, asecond allocated resource identifier and associated second presence code(URI-A/ProSe Code-A), of the set of presence codes, for use inretrieving the first content from a second mobile device (UE-A) inproximity to the requesting mobile device. Where the request also refersto a second object (e.g., Objects 3, 4, and/or 5), the content response(408) also includes, as a second link the second object, a thirdresource identifier for use in retrieving the second content from theserver or another non-mobile device entity.

In the foregoing specification, specific embodiments have beendescribed. However, one of ordinary skill in the art appreciates thatvarious modifications and changes can be made without departing from thescope of the disclosure as set forth in the claims below. Accordingly,the specification and figures are to be regarded in an illustrativerather than a restrictive sense, and all such modifications are intendedto be included within the scope of present teachings.

The benefits, advantages, solutions to problems, and any element(s) thatmay cause any benefit, advantage, or solution to occur or become morepronounced are not to be construed as a critical, required, or essentialfeatures or elements of any or all the claims. The invention is definedsolely by the appended claims including any amendments made during thependency of this application and all equivalents of those claims asissued.

Moreover in this document, relational terms such as first and second,top and bottom, and the like may be used solely to distinguish oneentity or action from another entity or action without necessarilyrequiring or implying any actual such relationship or order between suchentities or actions. The terms “comprises,” “comprising,” “has”,“having,” “includes”, “including,” “contains”, “containing” or any othervariation thereof, are intended to cover a non-exclusive inclusion, suchthat a process, method, article, or apparatus that comprises, has,includes, contains a list of elements does not include only thoseelements but may include other elements not expressly listed or inherentto such process, method, article, or apparatus. An element proceeded by“comprises . . . a”, “has . . . a”, “includes . . . a”, “contains . . .a” does not, without more constraints, preclude the existence ofadditional identical elements in the process, method, article, orapparatus that comprises, has, includes, contains the element. The terms“a” and “an” are defined as one or more unless explicitly statedotherwise herein. The terms “substantially”, “essentially”,“approximately”, “about” or any other version thereof, are defined asbeing close to as understood by one of ordinary skill in the art, and inone non-limiting embodiment the term is defined to be within 10%, inanother embodiment within 5%, in another embodiment within 1% and inanother embodiment within 0.5%. The term “coupled” as used herein isdefined as connected, although not necessarily directly and notnecessarily mechanically. A device or structure that is “configured” ina certain way is configured in at least that way, but may also beconfigured in ways that are not listed.

It will be appreciated that some embodiments may be comprised of one ormore generic or specialized processors (or “processing devices”) such asmicroprocessors, digital signal processors, customized processors andfield programmable gate arrays (FPGAs) and unique stored programinstructions (including both software and firmware) that control the oneor more processors to implement, in conjunction with certainnon-processor circuits, some, most, or all of the functions of themethod and/or apparatus described herein. Alternatively, some or allfunctions could be implemented by a state machine that has no storedprogram instructions, or in one or more application specific integratedcircuits (ASICs), in which each function or some combinations of certainof the functions are implemented as custom logic. Of course, acombination of the two approaches could be used.

Moreover, an embodiment can be implemented as a computer-readablestorage medium having computer readable code stored thereon forprogramming a computer (e.g., comprising a processor) to perform amethod as described and claimed herein. Examples of suchcomputer-readable storage mediums include, but are not limited to, ahard disk, a CD-ROM, an optical storage device, a magnetic storagedevice, a ROM (Read Only Memory), a PROM (Programmable Read OnlyMemory), an EPROM (Erasable Programmable Read Only Memory), an EEPROM(Electrically Erasable Programmable Read Only Memory), and a Flashmemory. Further, it is expected that one of ordinary skill,notwithstanding possibly significant effort and many design choicesmotivated by, for example, available time, current technology, andeconomic considerations, when guided by the concepts and principlesdisclosed herein will be readily capable of generating such softwareinstructions and programs and ICs with minimal experimentation.

The Abstract of the Disclosure is provided to allow the reader toquickly ascertain the nature of the technical disclosure. It issubmitted with the understanding that it will not be used to interpretor limit the scope or meaning of the claims. In addition, in theforegoing Detailed Description, it can be seen that various features aregrouped together in various embodiments for the purpose of streamliningthe disclosure. This method of disclosure is not to be interpreted asreflecting an intention that the claimed embodiments require morefeatures than are expressly recited in each claim. Rather, as thefollowing claims reflect, inventive subject matter lies in less than allfeatures of a single disclosed embodiment. Thus the following claims arehereby incorporated into the Detailed Description, with each claimstanding on its own as a separately claimed subject matter.

I claim:
 1. A method performed by a server for enabling distribution ofcontent using a mobile device, the method comprising: receiving, from afirst mobile device, a first request for first content identified by afirst resource identifier, wherein the first content comprises a firstobject referred to in the first request, and wherein the first requestalso refers to a second object; receiving, with the first request forthe first content, a set of presence codes that each indicate proximityof a mobile device without identifying a user of the mobile device,wherein the set of presence codes includes a first presence code for thefirst mobile device and at least one other presence code for one or moremobile devices in proximity to the first mobile device; selecting a setof allocated resource identifiers associated with one or more presencecodes, in the set of presence codes, for one or more of the mobiledevices in proximity to the first mobile device having the first contentcached therein, wherein each allocated resource identifier in the set isdifferent than the first resource identifier, and wherein the set ofallocated resource identifiers includes second and third allocatedresource identifiers and associated second and third presence codes, ofthe set of presence codes, to retrieve the first and second objects fromtwo different mobile devices in proximity to the first mobile device;sending, to the first mobile device, the set of allocated resourceidentifiers and associated presence codes to retrieve the first contentcached in the one or more mobile devices in proximity to the firstmobile device.
 2. The method of claim 1 further comprising successfullyvalidating the first presence code, wherein the set of allocatedresource identifiers and associated presence codes is sent in responseto successfully validating the first presence code.
 3. The method ofclaim 2, wherein successfully validating the first presence codeincludes exchanging messaging between the server and a first proximityservices function within a first 3rd Generation Partnership Projectnetwork with which the server is authorized to communicate.
 4. Themethod of claim 3, wherein successfully validating the first presencecode further includes a message exchange between the first proximityservices function and a second proximity services function within asecond 3rd Generation Partnership Project network subscribed to by atleast one of the first mobile device or a user of the first mobiledevice.
 5. The method of claim 1, wherein selecting the set of allocatedresource identifiers comprises at least one of: validating the one ormore presence codes for the one or more mobile devices in proximity tothe first mobile device having the first content cached therein; orverifying that the one or more mobile devices in proximity to the firstmobile device having the first content cached therein are authorized forproximity communications.
 6. The method of claim 1, wherein the set ofallocated resource identifiers and associated presence codes containsonly a single allocated resource identifier and associated presencecode, the method further comprising: receiving, with the first requestfor the first content, a plurality of quality indicators that eachindicates quality of communication between the first mobile device and adifferent one of the mobile devices in proximity to the first mobiledevice, which has a presence code in the set of presence codes; whereinthe single allocated resource identifier and the associated presencecode is selected, based on the plurality of quality indicators, frommultiple allocated resource identifiers and associated presence codesfor multiple mobile devices in proximity to the first mobile devicehaving the first content cached therein.
 7. The method of claim 1,wherein the set of allocated resource identifiers and associatedpresence codes includes multiple allocated resource identifiers andassociated presence codes to enable the first mobile device to select asingle one of the multiple allocated resource identifiers and associatedpresence codes for use in retrieving the first content cached in one ofthe mobile devices in proximity to the first mobile device.
 8. Themethod of claim 1 further comprising: receiving, from a second mobiledevice, a second request for the first content identified by the firstresource identifier; receiving, with the second request for the firstcontent, a fourth presence code that indicates proximity of the secondmobile device without identifying a user of the second mobile device;sending the first content to the second mobile device; sending with thefirst content a fourth allocated resource identifier that is differentthan the first resource identifier, wherein the fourth allocatedresource identifier is associated with the fourth presence code for thesecond mobile device and enables receiving the first content cached inthe second mobile device.
 9. The method of claim 8, wherein the set ofpresence codes received from the first mobile device includes the fourthpresence code, and the set of allocated resource identifiers andassociated presence codes sent to the first mobile device includes thefourth allocated resource identifier and the fourth presence code. 10.The method of claim 1, wherein sending the set of allocated resourceidentifiers comprises sending a content response to the first mobiledevice that includes, as a first link to the first object, a fourthallocated resource identifier and associated fourth presence code, ofthe set of presence codes, for use in retrieving the first content froma second mobile device in proximity to the first mobile device.
 11. Themethod of claim 10, wherein the content response also includes, as asecond link to the second object, a fifth resource identifier for use inretrieving second content from the server or another non-mobile deviceentity.
 12. The method of claim 1, wherein the first request is for aweb page referring to the first content as the first object.
 13. Aserver configured for enabling distribution of content using a mobiledevice, the server comprising: a processor and communication interfaceoperatively coupled and collectively configured to: receive, from afirst mobile device, a first request for first content identified by afirst resource identifier; receive, with the first request for the firstcontent, a first presence code that indicates proximity of the firstmobile device to other mobile devices without identifying a user of thefirst mobile device; send the first content to the first mobile device;send with the first content a second allocated resource identifier thatis different than the first resource identifier, wherein the secondallocated resource identifier is associated with the first presence codefor the first mobile device and enables the other mobile devices toreceive the first content cached in the first mobile device.
 14. Amethod performed by a first mobile device for enabling secondarydistribution of content received from a server, the method comprising:sending, to the server, a first request for first content identified bya first resource identifier, wherein the first content comprises a firstobject referred to in the first request, and wherein the first requestalso refers to a second object; sending, with the first request for thefirst content, a set of presence codes that each indicate proximity of amobile device without identifying a user of the mobile device, whereinthe set of presence codes includes a first presence code for the firstmobile device, a second presence code for a second mobile device, and athird presence code for a third mobile device; receiving, from theserver, at least second and third allocated resource identifiers andassociated second and third presence codes, wherein each of the secondand third allocated resource identifiers is different from the firstresource identifier, and receiving the second and third allocatedresource identifiers and the associated second and third presence codesredirects receipt of the first and second objects from the server to thesecond and third mobile devices in proximity to the first mobile device.15. The method of claim 14, wherein sending each presence code comprisessending a proximity-related services code allocated by a proximityservices function of a 3rd Generation Partnership Project networksubscribed to by at least one of the mobile devices to which theproximity-related services code was allocated or a user of the mobiledevice.
 16. The method of claim 14 further comprising: receiving, fromthe server, a fourth allocated resource identifier, which authorizesreceipt of the first content when cached in the first mobile device;receiving, from a fourth mobile device, a second request for the firstcontent; sending the first content to the fourth mobile device when thefirst content is identified in the second request by the fourthallocated resource identifier associated with the first presence codefor the first mobile device, and withholding sending the first contentto the fourth mobile device when the first content is identified in thesecond request by the first resource identifier.
 17. The method of claim14, wherein the set of presence codes includes one or more additionalpresence codes for one or more additional mobile devices, the methodfurther comprising: sending, with the first request for the firstcontent, a set of quality indicators indicating quality of communicationbetween the first mobile device and the second mobile device andindicating quality of communication between the first mobile device andeach of the one or more additional mobile devices.
 18. The method ofclaim 14, wherein the set of presence codes includes one or moreadditional presence codes for one or more additional mobile devices, themethod further comprising: determining a set of quality indicatorsindicating quality of communication between the first mobile device andthe second mobile device and indicating quality of communication betweenthe first mobile device and each of the one or more additional mobiledevices; receiving a plurality of allocated resource identifiers andassociated presence codes, which includes the second allocated resourceidentifier, wherein each received allocated resource indicatorauthorizes receipt of the first content from a different one of themobile devices having a presence code in the set of presence codes;selecting, based on the set of quality indicators, one of the receivedallocated resource identifiers and associated presence codes for use inrequesting the first content from the mobile device to which theselected resource identifier was allocated.